| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.7.5.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.7.5 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_7_5_Manage_Transitions_of_Care_and_Discharged_Patients |
| Title | AS.7.5 Manage Transitions of Care and Discharged Patients (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide a means to manage outstanding patient issues after the encounter, for transits of care and discharge. |
| Purpose | After the completion of an encounter, a number of tasks may remain for discharge planning, patient instructions and transitions of care. There may be outstanding laboratory tests (i.e. blood cultures) radiology interpretations, or other tasks such as arrangement of home health aids (VNA), transportation or calls to the patient's primary care provider during office hours to establish follow-up. There must be a way to track and document these tasks after the conclusion of the encounter. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide a means to manage outstanding patient issues after the encounter, for transits of care and discharge.
After the completion of an encounter, a number of tasks may remain for discharge planning, patient instructions and transitions of care. There may be outstanding laboratory tests (i.e. blood cultures) radiology interpretations, or other tasks such as arrangement of home health aids (VNA), transportation or calls to the patient's primary care provider during office hours to establish follow-up. There must be a way to track and document these tasks after the conclusion of the encounter.
| AS.7.5#01 | SHOULD |
The system SHOULD provide the ability to manage post-encounter tasks (e.g., discharge planning, patient instructions, transfer activities). |
| AS.7.5#02 | SHOULD |
The system SHOULD provide the ability to tag the patient as a transfer patient (e.g., hospital-to-hospital, birthing facility, and long-term-care-facility to hospital). |
| AS.7.5#03 | MAY |
The system MAY provide the ability to link transfer facility demographic information to the transfer patient. |
| AS.7.5#04 | MAY |
The system MAY provide the ability to capture the transfer mode of transportation (e.g., ambulance, airplane). |
| AS.7.5#05 | MAY |
The system MAY provide the ability to capture transportation provider demographics. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.7.5",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide a means to manage outstanding patient issues after the encounter, for transits of care and discharge.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>After the completion of an encounter, a number of tasks may remain for discharge planning, patient instructions and transitions of care. There may be outstanding laboratory tests (i.e. blood cultures) radiology interpretations, or other tasks such as arrangement of home health aids (VNA), transportation or calls to the patient's primary care provider during office hours to establish follow-up. There must be a way to track and document these tasks after the conclusion of the encounter.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.5#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage post-encounter tasks (e.g., discharge planning, patient instructions, transfer activities).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.5#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to tag the patient as a transfer patient (e.g., hospital-to-hospital, birthing facility, and long-term-care-facility to hospital).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.5#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to link transfer facility demographic information to the transfer patient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.5#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture the transfer mode of transportation (e.g., ambulance, airplane).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.5#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture transportation provider demographics.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.7.5",
"version" : "2.1.0",
"name" : "AS_7_5_Manage_Transitions_of_Care_and_Discharged_Patients",
"title" : "AS.7.5 Manage Transitions of Care and Discharged Patients (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide a means to manage outstanding patient issues after the encounter, for transits of care and discharge.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "After the completion of an encounter, a number of tasks may remain for discharge planning, patient instructions and transitions of care. There may be outstanding laboratory tests (i.e. blood cultures) radiology interpretations, or other tasks such as arrangement of home health aids (VNA), transportation or calls to the patient's primary care provider during office hours to establish follow-up. There must be a way to track and document these tasks after the conclusion of the encounter.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.5-01",
"label" : "AS.7.5#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage post-encounter tasks (e.g., discharge planning, patient instructions, transfer activities)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.5-02",
"label" : "AS.7.5#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to tag the patient as a transfer patient (e.g., hospital-to-hospital, birthing facility, and long-term-care-facility to hospital)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.5-03",
"label" : "AS.7.5#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to link transfer facility demographic information to the transfer patient."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.5-04",
"label" : "AS.7.5#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture the transfer mode of transportation (e.g., ambulance, airplane)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.5-05",
"label" : "AS.7.5#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture transportation provider demographics."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.